Global Setup
Global Options
Security Role [Manage Recon Setup]: Anyone assigned to this OneStream User Group is considered a super user who can configure any aspect of Account Reconciliations and also prepare, approve, comment, or view any reconciliation. This role is also referred to as the Reconciliations Global Admin. The default setting is the standard Administrators User Group.
NOTE: Anyone in the Administrators User Group is a OneStream System Administrator and, by default, can perform any of the same duties as a Reconciliations Global Admin.
Different from the OneStream System Administrator can be someone in the Administer Application Security Role User Group, which is configured under the Application tab and then in Security Roles. This User Group could be different from a System Administrator if the Administrators User Group is not assigned. If it is desired for anyone with this OneStream application’s Administer Application Security Role to also play the role of Reconciliations Global Admin, include that same User Group as a member of the User Group assigned to Security Role [Manage Recon Setup].
Security Role [Recon View Only]
This group can see reconciliations but cannot make any changes or log any reconciliation line items. This group must also have Access Group privileges to the workflow profiles where reconciliations are managed.
All Recons Require R-Doc
If set to True, each reconciliation that is not auto reconciled must have an R-Doc attached in order to click the Complete button.
Enable Mass Actions
Default values are False. If set to True, users can set multiple reconciliations to the same status at one time. If set to False, the buttons for mass actions do not display on the reconciliation workspace.
-
Prepare - Preparer can complete or recall multiple reconciliations.
-
Approve - Approver can approve, unapprove, or reject multiple reconciliations.
Process Recons on Complete Workflow
Setting this to True initiates Process Reconciliations before marking the workflow as completed. If new reconciliations are discovered or balances have changed, then the workflow cannot be completed.
NOTE: The Process Reconciliations action performed as part of the Complete workflow step is an in-line action. Running Process at the Base Input or Review level are Data Management jobs.
Source Scenario
This is typically the "Actual” scenario. When Discover is performed during reconciliation, this is the scenario queried for balances.
Recon Scenario
Set this up as a scenario separate from Actual. In this document, we are using an example of a scenario called ActualAR. This is a mirror of Actual but assigned a different scenario type, so a different workflow profile can be used with it, therefore it can have separate workflow locking from the Actual scenario type scenarios.
Recon Account Dimension
Select the Account dimension containing the accounts to be reconciled.
Recon Account Member Filter
Enter an account-based member filter used to query a list of accounts to reconcile. For example:
A#[Balance Sheet].Base, A#1000, A#2000.Base
If Extensible Dimensionality is being used on the Accounts dimension in this application, this member filter must be adjusted to query accounts differently across each cube. This is because an account could be a base member in one Account dimension and a parent in another. Here is an example of this syntax:
A#[Balance Sheet].Base.Options(Cube=[GolfStream], ScenarioType=Actual),A#[Balance Sheet].Base.Options(Cube=[Houston], ScenarioType=Actual)
Auto Create Recon Definition
If set to the default of True, when a user clicks Discover on the Reconciliation’s Definition page or clicks Process, a Reconciliation Definition is added for any account in the Account List that does not yet have one.
Email Connection
The named email connection used for notifications. The name of the connections in this drop list derives from the initial server configuration.
Recon Definition Email Notification Types
These all have a default value of False. If set to True, an email is sent to those in the main Security Group(Manage Recon Setup) under Global Options when these events happen.
-
New OneStream Account(s): A new account is included in the Account List after running Discover or Process.
-
New Recon(s) Discovered: New Reconciliation Inventory items are found after running Discover or Process.
-
Balance Changed: A reconciled balance was changed either after it was marked Complete or set to In Process and is different from the original value.
Status Email Notification Types
If set to True, when these reconciliation statuses change, an email is sent to users who are individually assigned to that Reconciliation Inventory item.
-
Completed- Email is sent to the Approver.
-
Rejected- Email is sent to the Preparer to notify them of the rejection.
-
Approved- Email is sent to the Preparer.
-
Unapproved- Email is sent to the Preparer.
-
Comment- Email is sent to the Preparer or Approver.
-
Balance Changed- Email is sent to the Preparer to notify them that the reconciliation must be completed again.
Emails are not sent to those who are assigned to the workflow profile. To set up email notifications for these status changes, place an Access Group directly on the Reconciliation Inventory items.
Multi-currency Reconciliations
This button enables the multi-currency features in the solution.
NOTE: After this button is selected and the settings saved, multi-currency cannot be disabled. It is strongly recommended that this feature be tested in a development application because you cannot revert to single currency reconciliations.
The impact of multi-currency is discussed throughout the document. Enabling multi-currency allows you to have a currency type set at the Source Account level (GL Account). The account currency type for each reconciliation item is maintained within the Reconciliation Inventory. This differs from the local currency (maintained on the Entity dimension) and reporting currency (maintained at the cube level). Therefore, each reconciliation item may have a different Account currency.
Reconciliations with a common Target Entity will have the same local currency, and all reconciliations within an application will have a single reporting currency. In addition, for reconciliations where multi-currency is enabled, account, local, and reporting currencies all display in the Account Reconciliations user interface.
Detail items may also be created using any currency type maintained in OneStream and are automatically translated to account, local, and reporting currencies upon Save. Also, Account Groups may be created for accounts or entities that have different currency types, allowing child reconciliations to be translated and aggregated to a single reconciling currency type, for each currency level, at the Account Group level.
FX Rate Type
Single Currency Solutions
The FX Rate Type that is being used to calculate the reconciliation balances on specific reports. Examples include ClosingRate or AverageRate. If this is not populated, no translated values are available in reports. This must be set even if multi-currency is enabled because some reconciliations within the Reconciliation Inventory may remain Single Currency.
Multi-currency Solutions
The FX Rate Type that is being used to translate reconciliation balances from local currency to account currency and from local currency to reporting currency. Translation from one currency level to another only occurs if the account and/or reporting balances are not loaded into Stage. Local currency is the base-level currency and is the level that is reconciled for single currency applications. Therefore, local balances are required for multi-currency reconciliations. This is also the rate type that is used to translate detail items from the detail currency type to the account, local, and reporting currency types. If this is not populated, translations do not occur.
FX Reporting Currency
Single Currency Solutions
The currency type used as the target currency for reports that translate values. If this is not populated, no translated values will be available on these reports.
Note on translation in certain reports: Account Reconciliations provides a translated value in certain reports for the convenience and analysis of the administrator or end user. This translated value is not stored but is calculated based on settings in Global Setup as the report is being processed. This is a simple translation being run that assumes a calculation similar to the “Direct” translation method of multiplying what is expected to be a Year to Date value by the FX Rate Type specified in Global Setup, however these are not the same translation algorithms being processed and no custom translation methods (i.e. Business Rules) are supported. These reports note that they are translated by listing this FX Reporting Currency in the right side of the report’s header section.
Example:
NOTE: To see the reports within the Reports and Analysis in different currency types, enable multi-currency.
Audit Files Use Target Name Only
This controls the naming convention for Audit Package files. When set to True, audit files that are created will only use the Target Account and Entity in the file name. When set to False, the audit files are created with the Source and Target Account and Entity in the file name. The default is set to not selected, (False).
NOTE: The check box should be selected if there is the possibility of the file name length exceeding the Windows limit of 260-character file names. If the file name exceeds 260-characters, the Audit Package file will not be generated. Windows 10 does enable users to change the 260-character limit by changing the Windows Group Policy.
Global Defaults
Default Reconciliation Definition
Default properties for all new Reconciliation Definitions created during the Discover process. See Reconciliation Definition for details on configuration. This only occurs if the Auto Create Recon Definition property of Global Options is selected
Default Reconciliation Properties
Default properties for all new Reconciliation Inventory items created during the Discover process. See Reconciliation Inventory for details on configuration.